Resource management using natural language processing tags

ABSTRACT

A natural language processing system that includes an artificial intelligence (AI) engine and a tag management engine. The AI engine is configured to receive a set of audio files and to identify concepts within the set of audio files. The AI engine is further configured to determine a usage frequency for each of the identified concepts and to generate an AI-defined tag for concepts with a usage frequency that is greater than a usage frequency threshold. The tag management engine is configured to receive an audio file, identify tags linked with the audio file, to determine an access frequency for the audio file within a predetermined time period, and to adjust the activity level of the tags based on the access frequency. The tag management engine is further configured to remove tags from the set of tags with an activity level that is less than a purge threshold.

TECHNICAL FIELD

The present disclosure relates generally to natural language audioprocessing, and more specifically to dynamically tagging audio samplesusing natural language processing.

BACKGROUND

Typically, audio files are large data files compared to other types ofdata files. In a computer system, storing a collection of audio filesconsumes a large amount of memory resources. This poses severaltechnical challenges for computer systems because these systems have toconstantly expand their data storage capabilities to provide sufficientstorage capacity for new audio files. As a system's memory resourcesapproach their maximum capacity, the number of memory resources forother operations performed by the system becomes reduced which begins todegrade the performance of the system.

Computer systems lack the capabilities to determine whether to storeaudio files or remove audio files from memory. Some systems may use amanual process which is performed by an operator to determine whether tostore or remove an audio file. However, audio files are typicallyseveral minutes in length. This means that for each audio file, theoperator may have to listen to several minutes of audio to determinewhether to store or remove an audio file. This process is time intensiveand causes a bottleneck that limits the speed that the system can acceptaudio files and its ability to manage its memory resources.

SUMMARY

Typically, audio files are large data files compared to other types ofdata files. In a computer system, storing a collection of audio filesconsumes a large amount of memory resources. This poses severaltechnical challenges for computer systems because these systems have toconstantly expand their data storage capabilities to provide sufficientstorage capacity for new audio files. As a system's memory resourcesapproach their maximum capacity, the number of memory resources forother operations performed by the system becomes reduced which begins todegrade the performance of the system. Computer systems lack thecapabilities to determine whether to store audio files or remove audiofiles from memory. Some systems may use a manual process which isperformed by an operator to determine whether to store or remove anaudio file. However, audio files are typically several minutes inlength. This means that for each audio file, the operator may have tolisten to several minutes of audio to determine whether to store orremove an audio file. This process is time intensive and causes abottleneck that limits the speed that the system can accept audio filesand its ability to manage its memory resources.

The natural language processing system described in the presentapplication employs natural language processing that allows a computersystem to 1) dynamically tag audio files based on their content, 2)generate new tags based on concepts observed within a set of audiofiles, 3) selectively store or remove audio files based on the tagsassociated with the audio files, 4) periodically purge tags from memorythat are not being frequently used, and 5) select a data storage deviceor location for an audio file based on the tags associated with theaudio file.

The natural language processing system provides a technical advantage bydynamically tagging audio files based on the content of the audio files.The natural language processing system tags audio files using acombination of user-defined tags, artificial intelligence (AI)-definedtags, context tags, and any other suitable type of tags. The naturallanguage processing system uses user-defined tags to indicate that anaudio file contains concepts that a user has previously identified. Thenatural language processing system uses AI-defined tags to indicate thatan audio file contains concepts that the natural language processingsystem has observed frequently in audio files. AI-tags provide atechnical advantage because they are dynamically generated based on thecontent of audio files that the natural language processing system haspreviously accessed. This feature allows the natural language processingsystem to learn and identify new concepts for tagging that may not havebeen previously identified by a user in the user-defined tags. Thenatural language processing system uses context tags to identifynon-verbal audio information that is present in an audio file. Forexample, context tags may be used to identify background noise, crowdnoise, traffic noise, speech rate, speech volume, or any other suitabletype of non-verbal information about the audio file. The naturallanguage processing system is configured to analyze the content of anaudio file and to modify the metadata of the audio file to include tagsbased on the observed content from the audio file.

The natural language processing system is configured to use the tagsassociated with an audio file to selectively store or remove the audiofile. In one embodiment, the natural language processing system may usetags linked with an audio file to determine a priority level or anactivity level for the audio file. The natural language processingsystem may use this information for determining whether to delete theaudio file or to store the audio file. For example, the natural languageprocessing system may determine and associate a priority level with anaudio file based on the tags associated with the audio file. Thepriority level is a value that indicates a level of priority orimportance associated with an audio file. For example, an audio filewith a relatively large numeric value may indicate that an audio filehas a high priority or is urgent. For instance, an audio file thatincludes information related to a system outage or an emergency may havea high priority level. An audio file with a smaller numeric value mayindicate that an audio file has a low priority or is not urgent. Forinstance, an audio file that includes a generic conversation may have alow priority level. The natural language processing system may determinewhether to store the audio file into memory based on the priority level.In one embodiment, the natural language processing system may deleteaudio files with a priority level that is less than a priority levelthreshold value. In this configuration, the natural language processingsystem is configured to efficiently manage resources by selectivelystoring and removing audio files based on the priority of an audio file.For example, audio files that are more urgent and have a higher prioritymay be stored while audio files that are not as critical may be deletedfrom memory.

In one embodiment, the natural language processing system is configuredto periodically determine how often tags are being used and to removetags that are not being used frequently. This configuration provides atechnological improvement that allows the natural language processingsystem to dynamically reduce file sizes and free up memory resources byremoving tags from memory that are not being frequently used.

In one embodiment, the natural language processing system is furtherconfigured to route an audio file to a particular data storage device orlocation based on tags or information determined about the audio file.In this configuration, the natural language processing system may selecta data storage device for an audio file based on data access speed,security features, or any other features that may be necessary for theaudio file. This process provides a technological improvement byallowing the natural language processing system to efficiently manageits data storage resources and to optimize the location where audiofiles are stored.

Certain embodiments of the present disclosure may include some, all, ornone of these advantages. These advantages and other features will bemore clearly understood from the following detailed description taken inconjunction with the accompanying drawings and claims.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of this disclosure, reference is nowmade to the following brief description, taken in connection with theaccompanying drawings and detailed description, wherein like referencenumerals represent like parts.

FIG. 1 is a schematic diagram of an embodiment of a natural languageprocessing system;

FIG. 2 is a schematic diagram of an embodiment of a natural languageprocessor for a natural language processing system;

FIG. 3 is a flowchart of an embodiment of an artificial intelligencetagging method for the natural language processing system;

FIG. 4 is a flowchart of an embodiment of an audio sample tagging methodfor the natural language processing system;

FIG. 5 is a flowchart of an embodiment of a selective audio samplestoring method for the natural language processing system; and

FIG. 6 is a flowchart of an embodiment of a tag management method forthe natural language processing system.

DETAILED DESCRIPTION

The natural language processing system disclosed herein employs naturallanguage processing that enables a computer system to 1) dynamically tagaudio files based on their content, 2) generate new tags based onconcepts observed within a set of audio files, 3) selectively store orremove audio files based on the tags associated with the audio files, 4)periodically purge tags from audio file or memory that are not beingfrequently used, and 5) select a data storage device or location for anaudio file based on the tags associated with the audio file.

FIGS. 1 and 2 are embodiments of a natural language processing systemand device, respectively, that are configured to provide the technicalfeatures described above. FIG. 3 is an embodiment of a processimplemented by the natural language processing system for generating newtags based on concepts observed within a set of audio files. FIG. 4 isan embodiment of a process implemented by the natural languageprocessing system for dynamically tagging audio files based on theircontent and selectively storing audio files based on their tags. FIG. 5is an embodiment of a process implemented by the natural languageprocessing system for selecting a data storage device or location basedon tags associated with an audio file. FIG. 6 is an embodiment of aprocess implemented by the natural language processing system forperiodically purging tags that are not being frequently used.

FIG. 1 is a schematic diagram of an embodiment of a natural languageprocessing system 100. The natural language processing system 100comprises one or more data sources 102, a natural language processor104, and one or more data storage devices 106. The natural languageprocessing system 100 is generally configured to receive audio files 116from the data sources 102, to tag the audio files 116 based on thecontent of the audio files 116, and to selectively store the audio file116 in a data storage device 106. This configuration provides atechnical improvement that enables a computer network to tag an audiofile 116 based on the content of the audio file 116 and to determinewhether to handle the audio file 116 to efficiently utilize availablehardware resources. For example, the natural language processing system100 may be implemented by a computer network to analyze the content of aset of audio files 116 and to determine whether to delete the audio file116, to store the audio file 116, or to route the audio file 116 to aparticular data storage device 106 or location based on the tagsassociated with the audio file 116. This configuration provides atechnical advantage that dynamically processes audio files 116 whichallows the computer network to efficiently manage its hardware resources(e.g. memory) while increasing the throughput and performance of thesystem.

Examples of data sources 102 include, but are not limited to, theInternet, social media, databases, memories, servers, computing devices,or any other suitable type of device. The natural language processingsystem 100 may comprise any suitable number of data sources 102 insignal communication with the natural language processor 104. Datasources 102 may be in signal communication with the natural languageprocessor 104 using any suitable type of wired or wireless connectionand/or communication protocol. Each data source 102 is configured tosend audio files 116, text files, images, and/or any other type of datato the natural language processor 104. In one embodiment, a data source102 is configured to periodically send data (e.g. audio files 116) tothe natural language processor 104. For example, a data source 102 maybe configured to send data to the natural language processor 104 inreal-time or at predetermined time intervals (e.g. hourly or daily). Inanother embodiment, a data source 102 is configured to send data inresponse to a data request from the natural language processor 104.

Examples of data storage devices 106 include, but are not limited to,databases, memories, hard drives, flash drives, servers, cloud servers,computing devices, or any other suitable type of data storing device.The natural language processing system 100 may comprise any suitablenumber of data storage devices 106 in signal communication with thenatural language processor 104. Data storage devices 106 may be insignal communication with the natural language processor 104 using anysuitable type of wired or wireless connection and/or communicationprotocol. Each data storage device 106 is configured to receive audiofiles 116, tags 118, priority levels 120, timestamps 122, activitylevels 124, text files, images, and/or any other type of data from thenatural language processor 104.

Audio files 116 may be any suitable type of audio files. Examples ofaudio file formats include, but are not limited to, way files, wmafiles, mp3 files, aiff files, or any other suitable audio file format.Audio files 116 comprise a combination of verbal (e.g. speech) andnon-verbal (e.g. background noise or speech characteristics)information. In one embodiment, the data storage device 106 may beconfigured to store text representations of the audio file 116. Forexample, the text representation may be result of a speech-to-texttranslation performed by the natural language processor 104.

In one embodiment, the tags 118 are metadata tags. In other embodiments,the tags 118 may be any other suitable type of tag as would beappreciated by one of ordinary skill in the art. The tags 118 maycomprise user-defined tags, AI-defined tags, context tags, and/or anyother suitable type of tags 118. The user-defined tags comprise tagsthat are linked with concepts defined or specified by a user. In oneembodiment, user-defined tags may be defined based on a set ofdictionary terms or business rules. An operator may provide apredetermined set of user-defined tags for the natural languageprocessor 104 to use for identifying concepts that are present withinaudio files 116. Concepts are any type of descriptor or identifier thatidentifies verbal or non-verbal information that may be present withinan audio file 116. Examples of concepts include, but are not limited to,news, errors, online services, customer service, locations, people,technology, law, medicine, or any other type of concept. Eachuser-defined tag may be linked with one or more concepts. The AI-definedtags are tags 118 that are generated by the AI engine 108 based onanalyzing the content of audio files 116 to identify concepts present inthe audio file 116. For example, the AI engine 108 may process andanalyze a set of audio files 116 to generate tags 118 identifying newconcepts that were observed from analyzing the audio files 116. EachAI-defined tag may be linked with one or more concepts. The context tagsmay comprise tags 118 linked with context information that is providedby a user or generated by the AI engine 108. Context tags and contextinformation identify non-verbal audio information that is present withinan audio file 116. Examples of non-verbal audio information include, butare not limited to, background noise, crowd noise, traffic noise, speechrate, speech volume, or any other suitable type of non-verbalinformation.

A priority level 120 is a value that indicates a level of priority orimportance associated with an audio file 116. For example, an audio file116 with a priority level set to a relatively large numeric value (orvice versa) may indicate that an audio file 116 has a high priority oris urgent. For instance, an audio file 116 that comprises informationrelated to a system outage or an emergency may have a high prioritylevel. An audio file 116 with a priority level set to a smaller numericvalue (or vice versa) may indicate that an audio file 116 has a lowpriority or is not urgent. For instance, an audio file 116 thatcomprises a generic conversation may have a low priority level.

An activity level 124 is a value that indicates how often an audio file116 has been accessed or used. For example, an audio file 116 with ahigh activity level 124 may indicate that the audio file 116 has beenaccessed frequently. An audio file 116 with a lower activity level 124may indicate that the audio file 116 is not used as often. The activitylevel 124 may be used as a metric to indicate how important an audiofile 116 is based on how frequently the audio file 116 is accessed.

Timestamps 122 comprise information about when an audio file 116 hasbeen accessed. For example, a time stamp 122 may comprise a date andtime that the audio file 122 was opened or played. Timestamps 122 may bein any suitable format as would be appreciated by one of ordinary skillin the art. In one embodiment, timestamps 122 may be stored as metadatalinked with audio files 116.

The natural language processor 104 comprises an artificial intelligence(AI) engine 108, a tagging engine 110, a tag management engine 112, anda resource allocation engine 114. In one embodiment, the AI-engine 108,the tagging engine 110, the tag management engine 110, and/or theresource allocation engine 114 may be configured to perform naturallanguage processing operations on data (e.g. audio files 116 or textfiles). Natural language processing operations include, but are notlimited to, operations such as speech recognition, speech parsing orsegmentation, identifying parts of speech, translating text-to-speech,translating speech-to-text, topic segmentation and recognition,sentiment analysis, optical character recognition, or any other suitabletype of operations. In another embodiment, natural language processingoperations may be performed by hardware and/or software external fromthe AI-engine 108, the tagging engine 110, the tag management engine110, and/or the resource allocation engine 114. For example, the naturallanguage processor 104 may further comprise a dedicated natural languageprocessing engine for processing data.

Dynamic Tag Generation

The AI engine 108 is configured to receive or access audio files 116from a data sources 102, to process the audio file 116 to identifyconcepts within the audio file 116, and to link AI-defined tags with theidentified concepts. In one embodiment, AI-defined tags are metadatatags that can be linked with the audio file 116 to identify conceptsthat are present in the audio file 116. For example, an audio file 116may include a conversation about a system error. The AI-engine 108 mayassociate tags 118 such as “system error,” “system fault,” or any othersuitable type of tags 118. The generated AI-defined tags may be used bythe natural language processor 104 for tagging concepts that are presentwithin audio files 116 and processing audio files 116.

The AI engine 108 is configured to generate AI-tags based on thefrequency that a concept appears or is used within one or more audiofiles 116. For example, the AI engine 108 may count the number of timesa concept occurs within an audio file 116 or a set of audio files 116and generate AI-defined tags 118 when the number of times the conceptsoccurs exceeds a usage frequency threshold value. In this configuration,the AI engine 108 provides a technological improvement by listening toaudio files 116 to identify new concepts that frequently occur withinone or more audio files 116. This allows the natural language processor104 to learn and identify new concepts for tagging that may not havebeen previously identified by a user.

Dynamic Audio File Tagging and Storing

The tagging engine 110 is configured to receive or access audio files116 from a data source 102, to process the audio file 116 to identifyconcepts that are present in the audio file 116, to determine whetherany of the identified concepts match concepts within a set of previouslydefined concepts, and to link the audio file 116 with tags 118 when theidentified concepts match concepts from the set of previously definedconcepts. The tagging engine 110 may link the audio file 116 withuser-defined tags, AI-defined tags, context tags, or any other suitabletypes of tags 118. In one embodiment, linking tags 118 with an audiofile 116 comprises modifying the metadata of the audio file 116 toinclude the tags 118. In other embodiments, the tagging engine 110 maylink tags 118 with an audio file 116 using any other suitable techniqueas would be appreciated by one of ordinary skill in the art.

The tagging engine 110 is configured to determine a priority level 120for an audio file 116 based on tags 118 (e.g. AI-defined tags)associated with the audio file 116 and to store an audio file 116 basedon a priority level 120 associated with the audio file 116. A prioritylevel 120 is a value that indicates a level of priority or importanceassociated with an audio file 116. For example, an audio file 116 with apriority level 120 set to a large numeric value (or vice versa) mayindicate that an audio file 116 has a high priority or is urgent. Forinstance, an audio file 116 that comprises information related to asystem outage or an emergency may have a high priority level 120. Anaudio file 116 with a priority level 120 set to a smaller numeric value(or vice versa) may indicate that an audio file 116 has a low priorityor is not urgent. For instance, an audio file 116 that comprises ageneric conversation may have a low priority level 120. The taggingengine 110 may determine to store the audio file 116 into memory whenthe priority level 120 associated with the audio file 116 exceeds apriority level threshold value. In one embodiment, the tagging engine110 may be configured to delete an audio file 116 when the prioritylevel 120 associated with the audio file 116 is less than a prioritylevel threshold value. In this example, the tagging engine 110 allowsthe natural language processing system 100 to conserve memory byremoving audio files 116 that are a low priority or that may not beimportant to the natural language processing system 100. In oneembodiment, the tagging engine 110 may be configured to modify themetadata of an audio file 116 to include the priority level 120associated with the audio file 116.

The tagging engine 110 is configured to use the priority level 120 ofthe audio file 116 to determine an activity level 124 for an audio file116 or tags 118 linked with an audio file 116. The activity level 124 isa value that indicates how often an audio file 116 has been accessed orused. For example, an audio file 116 with a high activity level 124 mayindicate that the audio file 116 has been accessed frequently. An audiofile 116 with a lower activity level 124 may indicate that the audiofile 116 is not used as often. The activity level 124 may be used as ametric to indicate how important or useful an audio file 116 is based onhow frequently the audio file 116 is accessed. The tagging engine 110may be further configured to modify the metadata for the audio file 116to include the determined activity level 124. In one embodiment, theactivity level 124 is an adjustable value that increases or decays overtime. The activity level 124 may be incremented or increased when anaudio file 116 is accessed within a predetermined time period. Theactivity level 124 may be decremented or decreased when the audio file116 has not been accessed within a predetermined time period. In thisconfiguration, the activity level 124 is a dynamic value that can beused as a metric to indicate how often an audio file 116 is beingaccessed or used over time. The activity level 124 of an audio file 116or tags 118 can be used by the natural language processing system 100for determining which audio files 116 and tags 118 to purge to conservememory resources.

Tag Usage Management

The tag management engine 112 is configured to receive or access audiofiles 116 from data sources 102, to process the audio files 116 toidentify tags 118 associated with the audio file 116, to determine anaccess frequency for the audio file 116, and to adjust an activity level124 for tags 118 associated with the audio file 116 based on the accessfrequency. The access frequency indicates how often the audio file 116has been accessed within a predetermined time period. For example, thetag management engine 112 may be configured to determine the accessfrequency based on a determined number of access timestamps 122 within apredetermined time period. In one embodiment, the tag management engine112 may be configured to increase the activity level 124 for tags 118when the access frequency is greater than an access frequency thresholdvalue. The tag management engine 112 may be configured to decrease theactivity level 124 for tags 118 when the access frequency is less thanan access frequency threshold value. In one embodiment, the tagmanagement engine 112 is configured to reduce the priority level 120associated with an audio file 116 in response to reducing the activitylevel 124 for tags 118 associated with the audio file 116.

The tag management engine 112 is configured to remove tags 118 from theaudio file 116 and/or from a set of stored tags 118 when the tags 118are not being used very often. For example, the tag management engine112 may be configured to determine whether any tags 118 have an activitylevel 124 below a purge threshold value and remove tags 118 from theaudio file 116 when their activity level 124 is less than the purgethreshold value. This configuration allows the tag management engine 112to dynamically reduce file sizes and free up memory resources byremoving tags 118 that are not being frequently used from memory.

The tag management engine 112 is configured to check whether an audiofile 116 is still linked with any tags 118 after removing tags 118 withan activity level 124 below the purge threshold value. The tagmanagement engine 112 may remove audio files 116 that are no longerassociated with any tags 118.

Selective Data Storing Based on Tags

The resource allocation engine 114 is configured to receive or access anaudio file 116 from data sources 102, to process the audio file 116 toidentify concepts within the audio file 116, to determine whether any ofthe identified concepts match concepts within a set of previouslydefined concepts, and to link the audio file 116 with the tags 118 whenthe identified concepts match concepts from the set of previouslydefined concepts. The resource allocation engine 114 may link the audiofile 116 with user-defined tags, AI-defined tags, context tags, or anyother suitable type of tags 118. In one embodiment, linking tags 118with an audio file 116 comprises modifying the metadata for the audiofile 116 to include the tags 118. In other embodiments, the resourceallocation engine 114 may link tags 118 with an audio file 116 using thetagging engine 110 or any other suitable technique as would beappreciated by one of ordinary skill in the art.

The resource allocation engine 114 is further configured to identify astorage location (e.g. a storage device 106) from among the plurality ofdata storage devices 106 based on the tags 118 associated with the audiofile 116 and to send the audio file 116 to the identified storage device106.

The resource allocation engine 114 may be configured to determine a dataaccess speed for the audio file 116 based on the tags 118 associatedwith the audio file 116 and to determine or select a storage locationfor the audio file 116 based on the determined data access speed. As anexample, an audio file 116 that is associated with a fast data accessspeed may be sent to a storage device 106 that allows fast access suchas a flash memory drive. As another example, an audio file 116 that isassociated with a slow data access speed may be sent to a storage device106 with a slower data access speed such as a tape drive. This processallows the resource allocation engine 114 to more efficiently manage theutilization of storage devices 106 for storing audio files 116. Slowerstorage devices 106 may provide a cost savings at the expense of dataaccess speeds. Conversely, faster storage devices 106 may provide higherdata access speed but may also be more expensive.

The resource allocation engine 114 may be configured to determine apriority level 120 for an audio file 116 based on the tags 118associated with the audio file 116 and to determine or select a storagelocation for the audio file 116 based on the determined priority level120. As an example, an audio file 116 that is associated with a highpriority level 120 may be sent to a storage device 106 that allows fastaccess, enhanced security, and/or any other features for high priorityaudio files 116. As another example, an audio file 116 that isassociated with a lower priority may be sent to a storage device 106with slower data access speed, basic security, and/or any other featuresfor low priority audio files 116. This process allows the resourceallocation engine 114 to more efficiently manage the utilization ofstorage devices 106 for storing audio files 116. Storage devices 106with varying levels of data access speed, security, and features can bedynamically selected for audio files 116 based on their priority level120.

The resource allocation engine 114 is configured to determine anactivity level 124 for an audio file 116 based on the priority level 120of the audio file 116. The resource allocation engine 114 may be furtherconfigured to modify the metadata for the audio file 116 to include thedetermined priority level 120 and/or activity level 124. In otherembodiments, the resource allocation engine 114 may determine and useany other information associated with an audio file 116 for selecting astorage location for the audio file 116.

Additional information about the natural language processor 104, the AIengine 108, the tagging engine 110, the tag management engine 110, andthe resource allocation engine 114 is described in FIG. 2.

FIG. 2 is a schematic diagram of an embodiment of a natural languageprocessor 104. The natural language processor 104 comprises a processor202, a memory 204, and a network interface 206. The natural languageprocessor 104 may be configured as shown or in any other suitableconfiguration.

The processor 202 comprises one or more processors operably coupled tothe memory 204. The processor 202 is any electronic circuitry including,but not limited to, state machines, one or more central processing unit(CPU) chips, logic units, cores (e.g. a multi-core processor),field-programmable gate array (FPGAs), application specific integratedcircuits (ASICs), or digital signal processors (DSPs). The processor 202may be a programmable logic device, a microcontroller, a microprocessor,or any suitable combination of the preceding. The processor 202 iscommunicatively coupled to and in signal communication with the memory204. The one or more processors are configured to process data and maybe implemented in hardware or software. For example, the processor 202may be 8-bit, 16-bit, 32-bit, 64-bit or of any other suitablearchitecture. The processor 202 may include an arithmetic logic unit(ALU) for performing arithmetic and logic operations, processorregisters that supply operands to the ALU and store the results of ALUoperations, and a control unit that fetches instructions from memory andexecutes them by directing the coordinated operations of the ALU,registers and other components.

The one or more processors are configured to implement variousinstructions. For example, the one or more processors are configured toexecute instructions to implement the AI engine 108, the tagging engine110, the tag management engine 112, and the resource allocation engine114. In this way, processor 202 may be a special purpose computerdesigned to implement function disclosed herein. In an embodiment, theAI engine 108, the tagging engine 110, the tag management engine 112,and the resource allocation engine 114 are each implemented using logicunits, FPGAs, ASICs, DSPs, or any other suitable hardware.

The AI engine 108, the tagging engine 110, the tag management engine112, and the resource management engine 114 are configured similar tothe AI-engine 108, the tagging engine 110, the tag management engine112, and the resource management engine 114 described in FIG. 1,respectively. An example of the AI engine 308 in operation is describedin FIG. 3. An example of the tagging engine 110 in operation isdescribed in FIG. 4. An example of the tag management engine 112 inoperation is described in FIG. 6. An example of the resource allocationengine 114 in operation is described in FIG. 5.

The memory 204 comprises one or more disks, tape drives, or solid-statedrives, and may be used as an over-flow data storage device, to storeprograms when such programs are selected for execution, and to storeinstructions and data that are read during program execution. The memory204 may be volatile or non-volatile and may comprise read-only memory(ROM), random-access memory (RAM), ternary content-addressable memory(TCAM), dynamic random-access memory (DRAM), and static random-accessmemory (SRAM). The memory 204 is operable to store tagging instructions208, tag management instructions 210, resource allocation instructions212, AI instructions 214, access frequency thresholds 216, purgethresholds 218, priority level thresholds 219, usage frequencythresholds 220, user-defined tags 222, AI-defined tags 224, context tags226, and audio files 116, and/or any other data or instructions. Thetagging instructions 208, the tag management instructions 210, theresource allocation instructions 212, and the AI instructions 214 maycomprise any suitable set of instructions, logic, rules, or codeoperable to execute the tagging engine 110, the tag management engine112, the resource allocation engine 114, and the AI engine 108,respectively.

The access frequency thresholds 216 are predefined values that are usedfor adjusting a priority level 120 associated with an audio file 116.For example, the natural language processor 104 may compare the accessfrequency of an audio file 116 to an access frequency threshold 216 todetermine whether to increase or decrease the priority level 120 of theaudio file 116. In one embodiment, the priority level 120 is increasedwhen the access frequency is greater than an access frequency threshold216 and the priority level 120 is decreased when the access frequency isless than the access frequency threshold 216.

The purge thresholds 218 are predefined values that are used fordetermining whether to remove or delete tags 118 from an audio file 116and/or from memory. For example, the natural language processor 104 maycompare the activity level 124 of a tag 118 to a purge threshold 218 todetermine whether to remove the tag 118 from an audio file 116. In oneembodiment, the tag 118 is removed from the audio file 116 when theactivity level 124 of the tag 118 is less than the purge threshold 218.

The priority level thresholds 219 are predefined values that may be usedto determine whether to store an audio file 116 into memory afterassociating one or more tags 118 with the audio file 116. For example,the natural language processor 104 may determine a priority level 120for an audio file 116 based on the tags 118 associated with the audiofile 106. The natural language processor 104 may then compare thedetermined priority level 120 to a priority level threshold 219 todetermine whether save or discard the audio file 116. The priority levelthreshold 219 is selected to allow the natural language processor 104 toconserve memory resources by discarding audio files 116 associated witha low priority level 120.

The usage frequency threshold 220 are predefined values that are usedfor determining whether to generate new tags 118. For example, thenatural language processor 104 may compare the number of times a conceptoccurs within an audio file 116 or a set of audio files 116 to the usagefrequency threshold 220 to determine whether to generate a new tag 118(e.g. an AI-defined tag 224). In one embodiment, an AI-defined tag 224is generated and stored when the number of times a concept occursexceeds a usage frequency threshold 220.

The user-defined tags 222, the AI-defined tags 224, and the context tags226 are similar to the user-defined tags, the AI-defined tags, and thecontext tags described in FIG. 1, respectively. The audio files 116 maybe configured similar to the audio files 116 previously described inFIG. 1.

The network interface 206 is configured to enable wired and/or wirelesscommunications. The network interface 206 is configured to communicatedata through a natural language processing system 100 and/or any othersystem or domain. For example, the network interface 206 may beconfigured for communication with data sources 102, data storage devices106, a modem, a switch, a router, a bridge, a server, or a client. Theprocessor 202 is configured to send and receive data using the networkinterface 206. The network interface 206 may be configured to anysuitable type of communication protocol as would be appreciated by oneof ordinary skill in the art.

Dynamic Tag Generation

FIG. 3 is a flowchart of an embodiment of an artificial intelligencetagging method 300 for the natural language processing system 100. Inone embodiment, method 300 may be employed by the AI engine 108 togenerate new AI-defined tags 224 based on concepts observed within a setof audio files 116.

At step 302, the AI engine 108 receives a set of audio files 116. In oneembodiment, the AI engine 108 accesses one or more data sources 102 todownload audio files 116 from the data sources 102. In anotherembodiment, the AI engine 108 may receive audio files 116 in response toa request sent to a data source 102. In another embodiment, the AIengine 108 may periodically receive audio files 116 from one or moredata sources 102. In this example, the AI engine 108 may receive audiofiles 116 at any suitable time interval. For example, the AI engine 108may receive audio files 116 every 5 minutes, every 30 minutes, hourly,every day, or at any other suitable time interval.

At step 304, the AI engine 108 identifies concepts within the set ofaudio files 116. The AI engine 108 may perform any suitable type ofsignal processing or natural language processing techniques for identifyconcepts within an audio file. For instance, the AI engine 108 mayperform topic segmentation and recognition to identify concepts fromwithin an audio file 116. As an example, the AI engine 108 may process aset of audio files 116 that comprise recordings of users callingtechnical support reporting issues with an online service. In thisexample, the AI engine 108 may identify concepts such as “onlineservices,” “errors,” and “technical support.”

At step 306, the AI engine 108 generates a set of tags 118 based on theidentified concepts. In one embodiment, the AI engine 108 may count thenumber of times a concept occurs within a set of audio files 116 andgenerate an AI-defined tag 224 when the number of times the conceptoccurs exceeds a usage frequency threshold 220. Continuing with theprevious example, the AI engine 108 may count the number of times thatthe concepts “online services” and “errors” have occurred and comparethe number of time these concepts have occurred to a usage frequencythreshold 220. When the number of times these concepts has occurredexceeds the usage frequency threshold 220, the AI engine 108 willgenerate a new tag 118 that identifies these concepts. For example, theAI engine 108 may generate an AI-defined tag 224 for “system error” or“online services error.” In this example, an issue may be a new issuethat was not previously known and the AI engine 108 enables the naturallanguage processing system 100 to generate tags 118 to identify andtrack the new issue. The AI engine 108 provides a technologicalimprovement by listening to audio files 116 to identify new conceptsthat frequently occur within a set of audio files 116. Thisfunctionality allows the natural language processor 104 to learn andidentify new concepts for tagging that may not have been previouslyidentified.

At step 308, the AI engine 108 set a priority level 120 for each tag118. For example, the AI engine 108 assigns tags 118 priority levels 120to indicate a level of importance or urgency to the system. For example,tags 118 related to errors or time sensitive concepts may be assigned ahigh priority level 120 (e.g. a larger numeric value). Tags 118 relatedto general concepts or non-time sensitive concepts may be assigned alower priority (e.g. a smaller numeric value). In some embodiments, step308 may be optional and may be omitted. Execution terminates at step310.

Dynamic Audio File Tagging and Storing

FIG. 4 is a flowchart of an embodiment of an audio sample tagging method400 for the natural language processing system 100. In one embodiment,method 400 may be implemented by the tagging engine 110 to link tagswith an audio file 116 based on concepts that are identified within theaudio file 116. Method 400 provides a technical improvement that enablesa computer network to tag an audio file 116 based on the content of theaudio file 116 which allows the computer network to determine how tohandle the audio file 116 to efficiently utilize available hardwareresources. This eliminates bottlenecks in the speed and performance ofthe system.

At step 402, the tagging engine 110 receives an audio file 116. In oneembodiment, the tagging engine 110 accesses a data source 102 todownload the audio files 116. In another embodiment, the tagging engine110 receives an audio file 116 in response to sending a request to adata source 102. In another embodiment, the tagging engine 110 mayperiodically receive an audio file 116 from one or more data sources102. In this example, the tagging engine 110 may receive audio files 116at any suitable time interval.

At step 404, the tagging engine 110 identifies observed concepts withinthe audio file 116. The tagging engine 110 may perform any suitable typeof signal processing or natural language processing techniques toidentify concepts within an audio file 116. For instance, the taggingengine 110 may perform topic segmentation and recognition to identifyconcepts from within an audio file 116.

At step 406, the tagging engine 110 determines whether any of theobserved concepts match user-defined concepts. The tagging engine 110compares the identified concepts from the audio file 116 with theconcepts linked with the stored user-defined tags 222 to determinewhether any of the user-defined concepts are present in the audio file116. The tagging engine 110 proceeds to step 408 in response todetermining that at least one of the observed concepts matches auser-defined concept. Otherwise, the tagging engine 110 proceeds to step410 in response to determining that none of the observed concepts matchthe user-defined concepts.

At step 408, the tagging engine 110 associates user-defined tags 222with the audio file 116. The tagging engine 110 links user-defined tags222 with the audio file 116 in response to determining that conceptsassociated with the user-defined tags 222 are present in the audio file116. In one embodiment, the tagging engine 110 associates theuser-defined tags 222 with the audio file 116 by modifying the metadataof the audio file 116 to include the user-defined tags 222.

Returning to step 406, the tagging engine 110 proceeds to step 410 inresponse to determining that none of the observed concepts match auser-defined concept. At step 410, the tagging engine 110 determineswhether any of the observed concepts match AI-defined concepts. Thetagging engine 110 compares the identified concepts from the audio file116 with the concepts linked with the stored AI-defined tags 224 todetermine whether any of the AI-defined concepts are present in theaudio file 116. The tagging engine 110 proceeds to step 412 in responseto determining that at least one of the observed concepts matches anAI-defined concept. Otherwise, the tagging engine 110 proceeds to step414 in response to determining that none of the observed concepts matchthe AI-defined concepts.

At step 412, the tagging engine 110 associates AI-defined tags 224 withthe audio file 116. The tagging engine 110 links the AI-defined tags 224with the audio file 116 in response to determining that conceptsassociated with the AI-defined tags 224 are present in the audio file116. In one embodiment, the tagging engine 110 associates the AI-definedtags 224 with the audio file 116 by modifying the metadata of the audiofile 116 to include the AI-defined tags 224.

Returning to step 410, the tagging engine 110 proceeds to step 414 inresponse to determining that none of the observed concepts match theAI-defined concepts. At step 414, the tagging engine 110 determineswhether any context information is available. The tagging engine 110 mayperform any suitable type of signal processing or natural languageprocessing techniques for identify context information within an audiofile 116. For instance, the tagging engine 110 may perform speechpattern recognition or noise recognition to identify context informationfrom within an audio file 116. The tagging engine 110 proceeds to step416 in response to determining that context information is available.Otherwise, the tagging engine 110 proceeds to step 418 in response todetermining that context information in unavailable.

At step 416, the tagging engine 110 associates context tags 226 with theaudio file 116 based on the identified context information. The taggingengine 110 links the context tags 226 with the audio file 116 inresponse to determining that context information associated with thecontext tags 226 is present in the audio file 116. In one embodiment,the tagging engine 110 associates the context tags 226 with the audiofile 116 by modifying the metadata of the audio file 116 to include thecontext tags 226.

Returning to step 414, the tagging engine 110 proceeds to step 418 inresponse to determining that context information in unavailable. At step418, the tagging engine 110 determines whether any tags 118 areassociated with the audio file 116. For example, the tagging engine 110may analyze the metadata of the audio file 116 to determine whether theaudio file 116 was linked with any user-defined tags 222, AI-definedtags 224, context tags 226, or any other type of tags 118. The taggingengine 110 proceeds to step 420 in response to determining that one ormore tags 118 are associated with the audio file 116. Otherwise, thetagging engine 110 proceeds to step 428 in response to determining thatthe audio file 116 is not associated with any tags 118.

At step 420, the tagging engine 110 determines a priority level 120 forthe audio file 116 based on the tags 118 associated with the audio file116. For example, the tagging engine 110 may assign the audio file 116with a relatively large numeric value to indicate that an audio file 116has a high priority or is urgent. For instance, the tagging engine 110may assign a high priority level 120 when the audio file 116 comprisestags 118 indicating the audio file 116 is related to a system outage oran emergency. The tagging engine 110 may assign the audio file 116 witha smaller numeric value may indicate that an audio file 116 has a lowpriority or is not urgent. For instance, the tagging engine 110 mayassign a low priority level 120 when the audio file 116 comprises tagsindicating the audio file 116 is a generic conversation.

At step 422, the tagging engine 110 determines whether the determinedpriority level 120 is greater than a priority level threshold 219. Thetagging engine 110 compares the determined priority level 120 to thepriority level threshold 219 to determine whether the priority level 120of the audio file 116 is greater than the priority level threshold 219.The tagging engine 110 proceeds to step 424 in response to determiningthat the determined priority level 120 is greater than the prioritylevel threshold 219. Otherwise, the tagging engine 110 proceeds to step428.

At step 424, the tagging engine 110 determines an activity level 124 forthe audio file 116. The tagging engine 110 determines how often theaudio file 116 has been accessed within a predetermined time period anddetermines an activity level 124 for the audio file 116 based on howoften the audio file 116 has been accessed.

At step 426, the tagging engine 110 stores the audio file 116 with themodified metadata into memory. For example, the tagging engine 110 maysend the audio file 116 with the modified metadata to a data storagedevice 106. In one embodiment, the tagging engine 110 may be configuredto modify the metadata of an audio file 116 to include the prioritylevel 120 and/or the activity level 124 associated with the audio file116 prior to sending the audio file 116 to the data storage device 106.

In one embodiment, the tagging engine 110 may segment or parse the audiofile 116 and may only store a portion of the audio file 116 to reducethe amount of memory used for storing the audio file 116. For example,the tagging engine 110 may use natural language processing operations tosegment the audio file 116 into smaller audio file 116 that contains thecontent previously identified and tagged by the tagging engine 110. Thisconfiguration allows the tagging engine 110 to conserve memory bystoring smaller audio files 116 that contains the content identified bythe tagging engine 110.

In one embodiment, the tagging engine 110 may be configured toadditionally or alternatively store a text translation or representationof the audio file 116. This configuration allows the tagging engine 110to conserve memory by storing the audio file 116 as a text file which isa smaller size file and consumes less memory than a traditional audiofile 116.

Returning to step 418, the tagging engine 110 proceeds to step 428 inresponse to determining that the audio file is not associated with anytags 118. At step 428, the tagging engine 110 deletes the audio file.This configuration allows the natural language processing system 100 toconserve memory by deleting audio files 116 that are determined to notbe important or useful to the natural language processing system 100.Execution of method 400 terminates at step 430.

Selective Data Storing Based on Tags

FIG. 5 is a flowchart of an embodiment of a selective audio samplestoring method 500 for the natural language processing system 100. Inone embodiment, method 500 is implemented by the resource allocationengine 114 to identify a storage location (i.e. a storage device 106)for an audio file 116 based on the tags 118 linked with the audio file116. Method 500 provides technical improvements over other systems byproviding the ability to selectively determine where to store audiofiles 116 based on the content within an audio file 116. For example,method 500 allows the computer network to select a data storage device106 and/or location for an audio file 116 based on information extractedfrom the audio file 116 such as requirements for data access speed andsecurity.

At step 502, the resource allocation engine 114 receives an audio file116. In one embodiment, the resource allocation engine 114 accesses adata source 102 to download the audio files 116. In another embodiment,the resource allocation engine 114 receives the audio file 116 inresponse to sending a request to a data source 102. In anotherembodiment, the resource allocation engine 114 may periodically receivean audio file 116 from one or more data sources 102. In this example,the resource allocation engine 114 may receive audio files 116 at anysuitable time interval.

At step 504, the resource allocation engine 114 identifies observedconcepts within the audio file 116. The resource allocation engine 114may perform any suitable type of signal processing or natural languageprocessing techniques for identify concepts within an audio file 116.For instance, the resource allocation engine 114 may perform topicsegmentation and recognition to identify concepts from within an audiofile 116.

At step 506, the resource allocation engine 114 determines whether anyof the observed concepts match user-defined concepts. The resourceallocation engine 114 compares the identified concepts from the audiofile 116 with the concepts linked with the stored user-defined tags 222to determine whether any of the user-defined concepts are present in theaudio file 116. The resource allocation engine 114 proceeds to step 508in response to determining that at least one of the observed conceptsmatches a user-defined concept. Otherwise, the resource allocationengine 114 proceeds to step 510 in response to determining that none ofthe observed concepts match the user-defined concepts.

At step 508, the resource allocation engine 114 associates user-definedtags 222 with the audio file 116. The resource allocation engine 114links user-defined tags 222 with the audio file 116 in response todetermining that concepts associated with the user-defined tags 222 arepresent in the audio file 116. In one embodiment, the resourceallocation engine 114 associates the user-defined tags 222 with theaudio file 116 by modifying the metadata of the audio file 116 toinclude the user-defined tags 222.

Returning to step 506, the resource allocation engine 114 proceeds tostep 510 in response to determining that none of the observed conceptsmatch a user-defined concept. At step 510, the resource allocationengine 114 determines whether any of the observed concepts matchAI-defined concepts. The resource allocation engine 114 compares theidentified concepts from the audio file 116 with the concepts linkedwith the stored AI-defined tags 224 to determine whether any of theAI-defined concepts are present in the audio file 116. The resourceallocation engine 114 proceeds to step 512 in response to determiningthat at least one of the observed concepts matches an AI-definedconcept. Otherwise, the resource allocation engine 114 proceeds to step514 in response to determining that none of the observed concepts matchthe AI-defined concepts.

At step 512, the resource allocation engine 114 associates AI-definedtags 224 with the audio file 116. The resource allocation engine 114links the AI-defined tags 224 with the audio file 116 in response todetermining that concepts associated with the AI-defined tags 224 arepresent in the audio file 116. In one embodiment, the resourceallocation engine 114 associates the AI-defined tags 224 with the audiofile 116 by modifying the metadata of the audio file 116 to include theAI-defined tags 224.

Returning to step 510, the resource allocation engine 114 proceeds tostep 514 in response to determining that none of the observed conceptsmatch the AI-defined concepts. At step 514, the resource allocationengine 114 determines whether any context information is available. Theresource allocation engine 114 may perform any suitable type of signalprocessing or natural language processing techniques for identifycontext information within an audio file 116. For instance, the resourceallocation engine 114 may perform speech pattern recognition or noiserecognition to identify context information from within an audio file116. The resource allocation engine 114 proceeds to step 516 in responseto determining that context information is available. Otherwise, theresource allocation engine 114 proceeds to step 518 in response todetermining that context information in unavailable.

At step 516, the resource allocation engine 114 associates context tags226 with the audio file 116 based on the identified context information.The resource allocation engine 114 links the context tags 226 with theaudio file 116 in response to determining that context informationassociated with the context tags 226 is present in the audio file 116.In one embodiment, the resource allocation engine 114 associates thecontext tags 226 with the audio file 116 by modifying the metadata ofthe audio file 116 to include the context tags 226.

Returning to step 514, the resource allocation engine 114 proceeds tostep 518 in response to determining that context information inunavailable. At step 518, the resource allocation engine 114 determineswhether any tags 118 are associated with the audio file 116. Forexample, the resource allocation engine 114 may analyze the metadata ofthe audio file 116 to determine whether the audio file 116 was linkedwith any user-defined tags 222, AI-defined tags 224, context tags 226,or any other type of tags 118. The resource allocation engine 114proceeds to step 520 in response to determining that one or more tags118 are associated with the audio file 116. Otherwise, the resourceallocation engine 114 proceeds to step 528 in response to determiningthat the audio file 116 is not associated with any tags 118.

At step 520, the resource allocation engine 114 determines a prioritylevel 120 based on the tags 118 associated with the audio file 116. Forexample, the resource allocation engine 114 may assign the audio file116 with a relatively large numeric value to indicate that an audio file116 has a high priority or is urgent. The resource allocation engine 114may assign the audio file 116 with a smaller numeric value may indicatethat an audio file 116 has a low priority or is not urgent.

At step 522, the resource allocation engine 114 determines an activitylevel 124 for the audio file 116. The resource allocation engine 114determines how often the audio file 116 has been access within apredetermined time period and determines an activity level 124 for theaudio file 116 based on how often the audio file 116 has been accessed.

At step 524, the resource allocation engine 114 determines a storagelocation for the audio file 116. The resource allocation engine 114selects a storage device 106 for the audio file 116 based on the tags118 associated with the audio file 116 and/or storage requirements forthe audio file 116. In one embodiment, tags 118 may be associated withparticular storage devices 106 or locations. For instance, a storagedevice 106 in a technical support server or location may be selected fortags 118 associated with system errors or issues. As another example, astorage device 106 in a fraud detection center may be selected for tags118 associated with fraud. In another embodiment, the resourceallocation engine 114 determines storage requirements for the audio file116 based on tags 118 associated with the audio file 116. Examples ofstorage requirements include, but are not limited to, priority levels120, activity levels 124, data access speeds, security requirements,accessibility, or any other suitable type of requirements. Thisconfiguration allows the resource management engine 114 to manage theutilization of storage devices 106 for storing audio files 116 byrouting audio files 116 to storage devices 106 where they are needed andcan be quickly accessed.

The resource allocation engine 114 may determine a data access speed forthe audio file 116 based on the tags 118 associated with the audio file116 and select a storage location for the audio file 116 based on thedetermined data access speed. For example, an audio file 116 that isassociated with a fast data access speed may be sent to a storage device106 that allows fast data access such as a flash memory drive. Asanother example, an audio file 116 that is associated with a slow dataaccess speed may be sent to a storage device 106 with a slower dataaccess speed such as a tape drive. This configuration allows theresource allocation engine 114 to more efficiently manage theutilization of storage devices 106 for storing audio files 116. Slowerstorage devices 106 may be more readily available but may offer lowerdata access speeds. Conversely, faster storage devices 106 may providehigher data access speed but their availability may be limited due tocosts.

The resource allocation engine 114 may determine a priority level 120for an audio file 116 based on the tags 118 associated with the audiofile 116 and select a storage location for the audio file 116 based onthe determined priority level 120. For example, an audio file 116 thatis associated with a high priority level 120 may be sent to a storagedevice 106 that allows fast data access speeds, enhanced security,and/or any other features for high priority audio files 116. This allowsaudio files 116 to be quickly accessed and reviewed. As another example,an audio file 116 that is associated with a lower priority level 120 maybe sent to a storage device 106 with slower data access speed, basicsecurity, and/or any other features for low priority audio files 116.This configuration allows the resource allocation engine 114 toefficiently manage the utilization of storage devices 106 for storingaudio files 116. Storage devices 106 with levels of data access speed,security features, and other features can be dynamically selected foraudio files 116 based on their priority level 120.

In other embodiments, the resource allocation engine 114 may select astorage device 106 for the audio file 116 based on any other suitableinformation or combination of information associated with the audio file116.

At step 526, the resource allocation engine 114 sends the audio file 116to the selected storage location. The resource allocation engine 114 maysend the audio file 116 to the selected storage device 106 using anysuitable communication protocol or technique as would be appreciated byone of ordinary skill in the art.

In one embodiment, the resource allocation engine 114 may segment orparse the audio file 116 and may only send a portion of the audio file116 to reduce the amount of memory used for storing the audio file 116.For example, the resource allocation engine 114 may use natural languageprocessing operations to segment the audio file 116 into smaller audiofile 116 that contains the content previously identified and tagged bythe resource allocation engine 114. This configuration allows theresource allocation engine 114 to conserve memory by storing smalleraudio files 116 that contains the content identified by the taggingengine 110.

In one embodiment, the resource allocation engine 114 may be configuredto additionally or alternatively send a text translation orrepresentation of the audio file 116. This configuration allows theresource allocation engine 114 to conserve memory by storing the audiofile 116 as a text file which is a smaller size file and consumes lessmemory than a traditional audio file 116.

Returning to step 518, the resource allocation engine 114 proceeds tostep 528 in response to determining that the audio file is notassociated with any tags 118. At step 528, the resource allocationengine 114 deletes the audio file 116. This configuration allows thenatural language processing system 100 to conserve memory by deletingaudio files 116 that are determined to not be important or useful to thenatural language processing system 100. Execution of method 500terminates at step 530.

In an alternative embodiment, one or more steps (e.g. steps 502-516) ofmethod 500 may be implemented by the tagging engine 110. For example,the tagging engine 110 may be employed to process an audio file 116 andto link the audio file 116 with tags 118 using a process similar to theprocess described in FIG. 4.

Tag Usage Management

FIG. 6 is a flowchart of an embodiment of a tag management method 600for the natural language processing system 100. In one embodiment,method 600 is implemented by the tag management engine 112 toperiodically remove tags 118 that are not being used frequently. Method600 allows the natural language processing system 100 to dynamicallyreduce file sizes and free up memory resources by removing tags 118 frommemory that are not being frequently used.

At step 602, the tag management engine 112 receives an audio file 116.In one embodiment, the tag management engine 112 accesses a data source102 to download the audio files 116. In another embodiment, the tagmanagement engine 112 may receive an audio file 116 in response to arequest to a data source 102. In another embodiment, the tag managementengine 112 may periodically receive an audio file 116 from one or moredata sources 102. In this example, the tag management engine 112 mayreceive audio files 116 at any suitable time interval.

At step 604, the tag management engine 112 identifies tags 118 linkedwith the audio file 116. For example, the tag management engine 112 mayanalyze the metadata of the audio file 116 to identify user-defined tags222, AI-defined tags 224, and context tags 226 linked with the audiofile 116.

At step 606, the tag management engine 112 determines an accessfrequency for the audio file 116 within a predetermined time period. Thetag management engine 112 determines how often the audio file 116 hasbeen access within the predetermined time period and uses the number oftimes that the audio file 116 has been access as the access frequency.For example, the tag management engine 112 may determine the accessfrequency based on the number of access timestamps 122 within thepredetermined time period.

At step 608, the tag management engine 112 determines whether the accessfrequency is greater an access frequency threshold 216. The tagmanagement engine 112 compares the determined access frequency to theaccess frequency threshold 216 to determine whether the access frequencyis greater than the access frequency threshold value 216. The tagmanagement engine 112 proceeds to step 610 in response to determiningthat the access frequency is above the access frequency threshold 216.Otherwise, the tag management engine 112 proceeds to step 612 inresponse to determining that the access frequency is less than theaccess frequency threshold 216.

At step 610, the tag management engine 112 increase the activity level124 for the identified tags 118 in response to determining that accessfrequency is greater than the access frequency threshold 216. Forexample, the tag management engine 112 may increment or increase thenumeric value representing the activity level 124 of a tag 118. In oneembodiment, the tag management engine 112 modifies the metadata of theaudio file 116 to reflect the new activity level 124 of the tag 118.

At step 612, the tag management engine 112 reduces the activity level124 for the identified tags 118 in response to determining that accessfrequency is less than the access frequency threshold 216. For example,the tag management engine 112 may decrement or decrease the numericvalue representing the activity level 124 of a tag 118. In oneembodiment, the tag management engine 112 modifies the metadata of theaudio file 116 to reflect the new activity level 124 of the tag 118.

At step 614, the tag management engine 112 determines whether theactivity level 124 of any of the tags 118 is below a purge threshold218. The tag management engine 112 compares the activity levels 124 ofthe tags 118 to the purge threshold 218 to determine whether theactivity level 124 of any of the tags 118 is less than the purgethreshold value 218. The tag management engine 112 proceeds to step 616in response to determining that the activity level 124 of one or moretags 118 is below the purge threshold 218. Otherwise, the tag managementengine 112 terminates method 600.

At step 616, the tag management engine 112 deletes or removes tags 118with an activity level 124 below the purge threshold 218. Thisconfiguration allows the tag management engine 112 to dynamically reducefile sizes and free up memory resources by removing tags 118 that arenot being frequently used. Execution of method 600 terminates at step618.

While several embodiments have been provided in the present disclosure,it should be understood that the disclosed systems and methods might beembodied in many other specific forms without departing from the spiritor scope of the present disclosure. The present examples are to beconsidered as illustrative and not restrictive, and the intention is notto be limited to the details given herein. For example, the variouselements or components may be combined or integrated in another systemor certain features may be omitted, or not implemented.

In addition, techniques, systems, subsystems, and methods described andillustrated in the various embodiments as discrete or separate may becombined or integrated with other systems, modules, techniques, ormethods without departing from the scope of the present disclosure.Other items shown or discussed as coupled or directly coupled orcommunicating with each other may be indirectly coupled or communicatingthrough some interface, device, or intermediate component whetherelectrically, mechanically, or otherwise. Other examples of changes,substitutions, and alterations are ascertainable by one skilled in theart and could be made without departing from the spirit and scopedisclosed herein.

To aid the Patent Office, and any readers of any patent issued on thisapplication in interpreting the claims appended hereto, applicants notethat they do not intend any of the appended claims to invoke 35 U.S.C. §112(f) as it exists on the date of filing hereof unless the words “meansfor” or “step for” are explicitly used in the particular claim.

1. A natural language processing system, comprising: one or more storagedevices operable to store: a set of audio files, wherein each audio fileis linked with one or more tags, wherein each tag is linked with anactivity level that decays over time; a network interface in signalcommunication with the one or more storage devices, wherein the networkinterface is configured to receive audio files from the one or morestorage devices; and a tag management engine implemented by a processoroperably coupled to the network interface, and configured to: receive anaudio file; identify tags linked with the audio file; determine anaccess frequency for the audio file, wherein the access frequencyindicates how often the audio file has been accessed within apredetermined time period; compare the access frequency of the audiofile to an access frequency threshold; reduce the activity level foreach of the identified tags in response to determining the accessfrequency is less than the access frequency threshold; increase theactivity level for each of the identified tags in response todetermining the access frequency is greater than the access frequencythreshold; compare the activity levels of the identified tags to a purgethreshold; and remove tags from the set of tags with an activity levelthat is less than the purge threshold.
 2. The system of claim 1, whereindetermining the access frequency comprises determining a number ofaccess timestamps within the predetermined time period.
 3. The system ofclaim 1, wherein the tag management engine is further configured to:determine the audio file is no longer linked with tags; and delete theaudio file in response to determining the audio file is no longer linkedwith tags.
 4. The system of claim 1, further comprising an artificialintelligence (AI) engine implemented by the processor, configured to:access the set of audio files; identify concepts within the set of audiofiles; determine a usage frequency for each of the identified concepts,wherein the usage frequency indicates how often each of the identifiedconcepts occurs within the set of audio files; compare the usagefrequency for each identified concept to a usage frequency threshold;generate an AI-defined tag for each identified concept with a usagefrequency that is greater than the usage frequency threshold, whereineach AI-defined tag is linked with the corresponding identified concept;and store the generated AI-defined tags.
 5. The system of claim 1,wherein the tag management engine is further configured to: access theset of audio files; identify observed context identifiers from the setof audio file, wherein a context identifier identifies non-verbal audioinformation from the set of audio files; generate context tags for eachidentified context identifier; and store the generated context tags. 6.The system of claim 1, wherein the tag management engine is furtherconfigured to: receive a set of user-defined tags, wherein eachuser-defined tag is linked with one or more concepts; and store theuser-defined tags.
 7. The system of claim 1, wherein tag managementengine is further configured to reduce a priority level associated withthe audio file in response to reducing the activity level for theidentified tags.
 8. A natural language processing method, comprising:receiving, by a tag management engine implemented by a processor, anaudio file, wherein the audio file is linked with one or more tags, andwherein the one or more tags are linked with an activity level thatdecays over time; identifying, by the tag management engine, tags linkedwith the audio file; determining, by the tag management engine, anaccess frequency for the audio file, wherein the access frequencyindicates how often the audio file has been accessed within apredetermined time period; comparing, by the tag management engine, theaccess frequency of the audio file to an access frequency threshold;reducing, by the tag management engine, the activity level for each ofthe identified tags in response to determining the access frequency isless than the access frequency threshold; increasing, by the tagmanagement engine, the activity level for each of the identified tags inresponse to determining the access frequency is greater than the accessfrequency threshold; comparing, by the tag management engine, theactivity levels of the identified tags to a purge threshold; andremoving, by the tag management engine, tags from the set of tags withan activity level that is less than the purge threshold.
 9. The methodof claim 8, wherein determining the access frequency comprisesdetermining a number of access timestamps within the predetermined timeperiod.
 10. The method of claim 8, further comprising: determining, bythe tag management engine, the audio file is no longer linked with tags;and deleting, by the tag management engine, the audio file in responseto determining the audio file is no longer linked with tags.
 11. Themethod of claim 8, further comprising: accessing, by an artificialintelligence (AI) engine implemented by the processor the set of audiofiles; identifying, by the AI engine, concepts within the set of audiofiles; determining, by the AI engine, a usage frequency for each of theidentified concepts, wherein the usage frequency indicates how ofteneach of the identified concepts occurs within the set of audio files;comparing, by the AI engine, the usage frequency for each identifiedconcept to a usage frequency threshold; generating, by the AI engine, anAI-defined tag for each identified concept with a usage frequency thatis greater than the usage frequency threshold, wherein each AI-definedtag is linked with the corresponding identified concept; and storing, bythe AI engine, the generated AI-defined tags.
 12. The method of claim 8,further comprising: accessing, by the tag management engine, the set ofaudio files; identifying, by the tag management engine, observed contextidentifiers from the set of audio file, wherein a context identifieridentifies non-verbal audio information from the set of audio files;generating, by the tag management engine, context tags for eachidentified context identifier; and storing, by the tag managementengine, the generated context tags.
 13. The method of claim 8, furthercomprising: receiving, by the tag management engine, a set ofuser-defined tags, wherein each user-defined tag is linked with one ormore concepts; and storing, by the tag management engine, theuser-defined tags.
 14. The method of claim 8, further comprisingreducing, by the tag management engine, a priority level associated withthe audio file in response to reducing the activity level for theidentified tags.
 15. A natural language processing device, comprising: anetwork interface configured to receive audio files from one or morestorage devices, wherein: each audio file is linked with one or moretags; and the one or more tags are linked with an activity level thatdecays over time; and a tag management engine implemented by a processoroperably coupled to the network interface, and configured to: receive anaudio file; identify tags linked with the audio file; determine anaccess frequency for the audio file, wherein the access frequencyindicates how often the audio file has been accessed within apredetermined time period; compare the access frequency of the audiofile to an access frequency threshold; reduce the activity level foreach of the identified tags in response to determining the accessfrequency is less than the access frequency threshold; increase theactivity level for each of the identified tags in response todetermining the access frequency is greater than the access frequencythreshold; compare the activity levels of the identified tags to a purgethreshold; and remove tags from the set of tags with an activity levelthat is less than the purge threshold.
 16. The device of claim 15,wherein determining the access frequency comprises determining a numberof access timestamps within the predetermined time period.
 17. Thedevice of claim 15, wherein the tag management engine is furtherconfigured to: determine the audio file is no longer linked with tags;and delete the audio file in response to determining the audio file isno longer linked with tags.
 18. The device of claim 15, furthercomprising an artificial intelligence (AI) engine implemented by theprocessor, configured to: access the set of audio files; identifyconcepts within the set of audio files; determine a usage frequency foreach of the identified concepts, wherein the usage frequency indicateshow often each of the identified concepts occurs within the set of audiofiles; compare the usage frequency for each identified concept to ausage frequency threshold; generate an AI-defined tag for eachidentified concept with a usage frequency that is greater than the usagefrequency threshold, wherein each AI-defined tag is linked with thecorresponding identified concept; and store the generated AI-definedtags.
 19. The device of claim 15, wherein the tag management engine isfurther configured to: access the set of audio files; identify observedcontext identifiers from the set of audio file, wherein a contextidentifier identifies non-verbal audio information from the set of audiofiles; generate context tags for each identified context identifier; andstore the generated context tags.
 20. The device of claim 15, whereintag management engine is further configured to reduce a priority levelassociated with the audio file in response to reducing the activitylevel for the identified tags.